With ClickWarrior installed, double-clicking an entry in a CodeWarrior project window or tapping [return] or [enter] while the project window is frontmost will open the selected .c, .cp, and/or .cpp files into BBEdit (instead of CodeWarrior).
———————— INSTALLATION
Drop ClickWarrior onto your System Folder icon and allow Finder to put it in its proper place. Restart and ClickWarrior will load. To remove ClickWarrior, open the Extensions folder in your System Folder and drag the ClickWarrior icon and drop it somewhere outside the System Folder hierarchy. Restart and ClickWarrior will not load.
———————— USAGE
To disable ClickWarrior for the duration of one double-click or [enter] or [return] keypress, hold down the control key. I know this isn't a particularly popular key on the Macintosh, but it so happens that all the other modifier keys already mean something when the user clicks in a project window.
———————— CAVEATS
ClickWarrior relies on exceedingly undocumented information obtained by reverse engineering both BBEdit 3.5 and the versions of CodeWarrior that shipped in the CW6 mailing. It's probable that the interface to CodeWarrior will break first, as it relies on trap patches and the structure of the project window's ListHandle. I may try to track changes in CodeWarrior, but it may not be possible forever. Then again perhaps CW 2.0 will also have AppleEvent support such that ClickWarrior is no longer necessary. (Please feel free to lobby Metrowerks to that effect!)
There is a bug in CodeWarrior, in which it will provide a bogus file spec when the file being requested hasn't been searched for by the CodeWarrior environment. This is most often seen in projects that are being converted from older versions of CodeWarrior, or projects on which a "Reset File Paths" command has been performed. With older versions of BBEdit and ClickWarrior, attempts to open these files would silently fail. As of BBEdit 3.5.1, an alert will be put up warning of CodeWarrior's mistake. To work around this problem, choose "Bring Up to Date", "Make",
or perform some other action that causes CodeWarrior to locate your files. After you've done so, CodeWarrior will return the proper information when asked, and the whole ClickWarrior/CodeWarrior/BBEdit setup will function as intended.
———————— ACKNOWLEDGEMENTS
— Avi Rappoport catalyzed my inspiration over maple sundae and fries.
— Rich Siegel exclaimed "What a disgusting hack! I love it!"
— The BBEdit beta tester mailing list tolerated my long binary posts.
— Donna Lee, my beloved spousal unit, manufactured an excuse to shoo me out of the house so I could come to the office on the 4th of July to get this infernal project out of my system.
———————— SUPPORT AND CONTACT INFORMATION
Neither Metrowerks (CodeWarrior) nor Bare Bones (BBEdit) have sanctioned ClickWarrior. I imagine they will not be interested in providing support for it. If you have problems with ClickWarrior, you should contact the author directly. Send email to <gurgle@dnai.com>.
———————— LICENSING
This program is freeware.
If you are selling or re-selling CodeWarrior or BBEdit, you have my blessing to redistribute ClickWarrior in any relevant fashion as long as you don't charge more than the cost to you of an unformatted floppy disk.
If you are a non-profit group, you may charge your standard rate. I applaud you.
If you are an online service, you may charge no more for ClickWarrior than you do for the least expensive file in your publically asccessible Macintosh developer file download library.
If you are anybody else, you may not charge more for the redistribution of ClickWarrior than the cost to you of an unformatted floppy disk. If you don't sell floppy disks, you may not charge for ClickWarrior. If you want to charge a premium just because you copied some stuff off the net onto a CD ROM, you're out of luck. Get a real skill.
Under no circumstances should you attempt to contact me in an effort to get me to sign a legal document giving you permission to redistribute my work. No claims of further distribution will excite me.
———————— VERSION HISTORY
1.0b1 was not publically released. It contained the baseline feature set and several bugs, including lack of support for lots of compilers even though such support was entirely feasible.
1.0b2 was released 07/05/95 to the BBEdit beta tester mailing list. It rectified some of the problems with 1.0b1. Some problems in that department remain.
1.0b3 was released 07/13/95 to the BBEdit beta tester mailing list. It fixed the problem of incorrectly intercepting the [return] and/or [enter] keys while a notification alert was frontmost.
1.0 was released 07/15/95 to the BBEdit tester mailing list. As soon as BBEdit 3.5 ships, it will be released to MacGifts and another appropriate internet entities. This version did not fix any bugs but had an updated 'vers' 1 resource to reflect its anointed status.
1.0.1 was released 10/18/95. This version adds support for more file name suffixes (specifically ".r" for Rez support, and some more C++ variations), and fixes a bug in the Apple Event interaction with BBEdit.
